Skip to main content
POST
/
merchant
/
invoice
/
external_gateway_invoice
/
mark_refunded
[Deprecated] Mark External Gateway Invoice As Refunded
curl --request POST \
  --url https://api.unibee.dev/merchant/invoice/external_gateway_invoice/mark_refunded \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "externalTransactionId": "<string>",
  "invoiceId": "<string>",
  "signature": "<string>",
  "timestamp": 123,
  "gatewayId": 123
}
'
{
  "code": 123,
  "data": {
    "invoiceId": "<string>",
    "refundId": "<string>",
    "status": "<string>"
  },
  "merchantId": 123,
  "message": "<string>",
  "redirect": "<string>",
  "requestId": "<string>"
}

Endpoint Overview

POST https://api.unibee.dev/merchant/invoice/external_gateway_invoice/mark_refunded Deprecated placeholder. External refund flow will be redesigned. Do not use this invoice-level API for new integrations.

Authorization

All UniBee Merchant API requests require authentication via API key.
HeaderRequiredDescription
AuthorizationYesBearer <your_api_key>
Content-TypeYesapplication/json (for request body)

Parameters

Parameters for this endpoint are listed below. The schema is also shown in the Try it panel.

Request body

NameTypeRequiredDescription
externalTransactionIdstringYesExternal refund transaction id from gateway
gatewayIdintegerNoOptional. External gateway id; omit to use invoice’s current gateway for auth
invoiceIdstringYesInvoice id
signaturestringYesHMAC-SHA256(gatewayKey, invoiceId|externalTransactionId|timestamp), hex
timestampintegerYesRequest timestamp, UTC seconds, used for expiry check

Request examples

cURL

curl -X POST "https://api.unibee.dev/merchant/invoice/external_gateway_invoice/mark_refunded" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "externalTransactionId": "id_example",
  "gatewayId": 0,
  "invoiceId": "id_example",
  "signature": "",
  "timestamp": 0
}'

Sandbox

curl -X POST "https://api-sandbox.unibee.top/merchant/invoice/external_gateway_invoice/mark_refunded" \
  -H "Authorization: Bearer YOUR_SANDBOX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "externalTransactionId": "id_example",
  "gatewayId": 0,
  "invoiceId": "id_example",
  "signature": "",
  "timestamp": 0
}'

Response

Success responses return a JSON envelope with code, data, message, redirect, and requestId. code 0 indicates success.
FieldTypeDescription
codeintegerResponse code. 0 = success
dataobjectResponse payload
data.invoiceIdstringInvoice id
data.refundIdstringCreated refund id
data.statusstringResult status, e.g. success
messagestringHuman-readable message
requestIdstringRequest ID for support

Error handling

HTTP statusMeaning
400Bad request — invalid or missing parameters. Check message in the body.
401Unauthorized — missing or invalid API key.
404Not found — invalid path or resource.
500Server error — retry with backoff.
When code in the response body is non-zero, check message for details. Use requestId when contacting support.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json

Deprecated placeholder. External refund flow will be redesigned. Do not use this invoice-level API for new integrations.

externalTransactionId
string<string>
required

External refund transaction id from gateway

invoiceId
string<string>
required

Invoice id

signature
string<string>
required

HMAC-SHA256(gatewayKey, invoiceId|externalTransactionId|timestamp), hex

timestamp
integer<int64>
required

Request timestamp, UTC seconds, used for expiry check

gatewayId
integer<int64>

Optional. External gateway id; omit to use invoice's current gateway for auth

Response

200 - application/json
code
integer<int>
data
object
merchantId
integer<int64>
message
string<string>
redirect
string<string>
requestId
string<string>